-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove type requirements #2670
Remove type requirements #2670
Conversation
…into sainati/remove-type-requirements
@dsainati1 Is this PR marked as a draft because the FLIP isn't approved yet, or is there still something missing code-wise? |
Yes, if the design is approved as-is, this implementation is complete, so it's ready to be reviewed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! 👏 The removal really cleans up the code a lot 👌
…into sainati/remove-type-requirements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎺 👏
…into sainati/remove-type-requirements
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:feature/stable-cadence commit 4c9643b Collapsed results for better readability
|
Codecov Report
@@ Coverage Diff @@
## feature/stable-cadence #2670 +/- ##
==========================================================
- Coverage 79.33% 79.21% -0.12%
==========================================================
Files 337 337
Lines 80485 80139 -346
==========================================================
- Hits 63851 63484 -367
- Misses 14335 14361 +26
+ Partials 2299 2294 -5
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Closes #1283
This removes support for type requirements from Cadence, as proposed in onflow/flips#118
master
branchFiles changed
in the Github PR explorer